Changes between Version 21 and Version 22 of Installing Pidgin

Timestamp:

Aug 16, 2007, 3:36:25 AM (16 years ago)

Author:

John Bailey

Comment:

Fix some CamelCase words so they don't reference non-existant wiki pages

Installing Pidgin

@@ -74 +74 @@
 That's a long story.  For starters,  MTN is frequently unusable because of changes in the code.  Bugs are introduced during the development process and are hopefully fixed before a release is made.  It is often the case that Pidgin MTN exhibits bad behavior due to features and bugfixes which are in a transitory state or which are not yet well understood.  These bad behaviors range from the harmless (maybe a graphical glitch in a dialog box) to the irritating (a particular protocol may not work), to the downright damaging (recently a bug in MTN destroyed the user's buddy lists).  While behaviors like this are acceptable to some users (particularly developers, who are used to such things), they tend to cause many Pidgin MTN users to contact Pidgin developers and report the same (usually egregious) bug over and over - using time which could be better spent fixing the bugs.
 
-A second major point involves public resources - an MTN checkout is not a cheap operation.  As many SourceForge users are aware, at various points in the recent past SourceForge CVS has been less than pleasant to work with.  This is, of course, because SourceForge hosts dozens and dozens of useful and active projects which use[ed] CVS as a primary method of source code collaboration.  Unfortunately, when too many users are poking around in that CVS just for the sake of poking around, it prevents other users who are trying to do work to improve those very same projects from accomplishing their tasks.  Naturally, this could  easily become true of our MTN offering as well. It is better for the community if an enterprising individual wishing to fix a particular bug [s]he has seen can get to the code and create a patch, even if this means that some users have to wait a few weeks for the next release to see what new features it might hold.
+A second major point involves public resources - an MTN pull is not a cheap operation.  As many !SourceForge users are aware, at various points in the past few years !SourceForge CVS has been less than pleasant to work with.  This is, of course, because !SourceForge hosts thousands of useful and active projects which use[d] CVS as a primary method of source code collaboration.  Unfortunately, when too many users are poking around in that CVS just for the sake of poking around, it prevents other users who are trying to do work to improve those very same projects from accomplishing their tasks.  Naturally, this could  easily become true of our MTN offering as well. It is better for the community if an enterprising individual wishing to fix a particular bug [s]he has seen can get to the code and create a patch, even if this means that some users have to wait a few weeks for the next release to see what new features it might hold.
 
 The third point is not a problem which has yet come up, but it is in the back of the mind of the developers who bring you Pidgin.  As a third-party IM client, Pidgin is not a priority (and indeed may be an irritant) for the IM service providers.  We do our best to keep Pidgin playing nice and being friendly on the IM networks it uses; however, at times there are bugs in the protocol support.  If a few dozen people are using this buggy client, the IM providers are not likely to go out of their way to do anything about it.  However, if hundreds of people are pointing an ill-behaved client at an IM server, the server administrators may be forced to take action.  (This is particularly likely if the buggy behavior is damaging in some way.)  Pidgin releases represent code which the Pidgin developers feel is relatively well-behaved and stable.  This includes not only the interface seen by Pidgin users, but the traffic seen by IM service providers.  Pidgin MTN bears no such guarantees.